Methods, systems and apparatus for automated generation of a flight log and a squawk list file

ABSTRACT

The disclosed embodiments relate to methods, systems and apparatus for automated generation a flight log and a squawk list file. A computer records a preliminary flight log data file (PFLDF), and automatically generates a preliminary squawk list file (PSLF) that includes a plurality of squawk events recorded while an aircraft is in flight. A wireless communication device includes a processor configured to execute a software application, a display that displays a graphical user interface that presents each squawk event from the PSLF for review, and an input system configured to receive inputs including an input for each particular squawk event. These inputs for each particular squawk event can be an edit input, an approval input, or a removal input. When all squawk events in the PSLF have been reviewed, the processor executes the software application to generate a final flight log and a final squawk list file (FSLF) that includes each of the squawk events from the PSLF that have been reviewed and approved for inclusion in the final squawk list.

CROSS REFERENCE TO RELATED APPLICATIONS

This is a continuation of U.S. patent application Ser. No. 14/906,958,filed on Jan. 22, 2016, which is a U.S. National-Stage entry under 35U.S.C. § 371 based on International Application No. PCT/US2014/047664,filed on Jul. 22, 2014, and which claims priority to United StatesProvisional Patent Application No. 61/857,279, filed Jul. 23, 2014,which are all incorporated in their entirety by reference.

TECHNICAL FIELD

Embodiments of the present invention generally relate to aircraft, andmore particularly relate to methods, systems and apparatus for automatedgeneration of a flight log and a squawk list file.

BACKGROUND OF THE INVENTION

Modern aircraft are often equipped with sophisticated systems, such asflight data recorders, which report information and store in-flightdata. In addition, ground-based systems support aircraft maintenance.

When an aircraft is in flight, it can be difficult to detect whensub-systems or components of an aircraft begin to operate abnormally,and/or to correctly diagnose the specific source that is causing thatsub-system or component to operate abnormally. While these abnormaloperating conditions may persist after the aircraft has landed, in manycases that is not true, which can make it even more difficult tocorrectly diagnose the specific source that is causing that sub-systemor component to operate abnormally.

There is a need for methods and systems for monitoring the health of anaircraft and the aircraft's various components and sub-systems. It wouldbe desirable to provide methods and systems that can automaticallydetect abnormal conditions that indicate when one or more sub-systems orcomponents of an aircraft have experienced a degradation in performance.It would also be desirable if such methods and systems can identify thespecific source(s) within those particular sub-systems or componentsthat are causing the degradation in performance so that correctiveactions can be taken with respect to the identified sub-systems orcomponents prior to fault or failure. It would also be desirable if suchmethods and systems execute automatically and do not require crewintervention. It would also be desirable to provide methods and systemsthat can be used to create reports that automatically document detailsregarding events that happened during the flight. Furthermore, otherdesirable features and characteristics of the present invention willbecome apparent from the subsequent detailed description and theappended claims, taken in conjunction with the accompanying drawings andthe foregoing technical field and background.

SUMMARY

The disclosed embodiments relate to methods, systems and wirelesscommunication devices for automated generation a flight log and a squawklist file. A computer records a preliminary flight log data file(PFLDF), records squawk events that occur while an aircraft is inflight, and automatically generates a preliminary squawk list file(PSLF) that includes a plurality of squawk events. A wirelesscommunication device includes a processor configured to execute asoftware application, a display configured to display a graphical userinterface that presents each squawk event from the PSLF for review, andan input system configured to receive inputs comprising an input foreach particular squawk event in the PSLF. These inputs for eachparticular squawk event in the PSLF can be an edit input, an approvalinput, or a removal input. In some implementations, the inputs can alsoinclude an addition input that specifies a new squawk event. When allsquawk events in the PSLF have been reviewed, the processor executes thesoftware application to generate a final flight log and a final squawklist file (FSLF) that includes each of the squawk events from the PSLFthat have been reviewed and approved for inclusion as squawk events tobe investigated for corrective action after the flight.

DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention will hereinafter be described inconjunction with the following drawing figures, wherein like numeralsdenote like elements, and

FIG. 1 is an integrated system for aircraft health and trend monitoringof an aircraft and the aircraft's various sub-systems in accordance withsome of the disclosed embodiments.

FIG. 2A is a perspective view of an aircraft that can be used inaccordance with some of the disclosed embodiments.

FIG. 2B is a block diagram of an Aircraft Health and Trend Monitoringsystem in accordance with an exemplary implementation of the disclosedembodiments.

FIG. 2C is a block diagram of some of an aircraft's various sub-systemsin accordance with an exemplary implementation of the disclosedembodiments.

FIG. 3 is a block diagram of portions of a ground support network inaccordance with one exemplary implementation of the disclosedembodiments.

FIG. 4 is a method in accordance with some of the disclosed embodiments.

FIG. 5 is a block diagram that illustrates a wireless communicationdevice in accordance with the disclosed embodiments.

FIGS. 6-12 are examples screens that can be displayed as part of agraphical user interface (GUI) that can be displayed at the wirelesscommunication device in accordance with the disclosed embodiments.

DESCRIPTION OF EXEMPLARY EMBODIMENTS

As used herein, the word “exemplary” means “serving as an example,instance, or illustration.” The following detailed description is merelyexemplary in nature and is not intended to limit the invention or theapplication and uses of the invention. Any embodiment described hereinas “exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments. All of the embodiments described inthis Detailed Description are exemplary embodiments provided to enablepersons skilled in the art to make or use the invention and not to limitthe scope of the invention which is defined by the claims. Furthermore,there is no intention to be bound by any expressed or implied theorypresented in the preceding technical field, background, brief summary orthe following detailed description.

The disclosed embodiments relate to methods, systems and computerprogram products for automated generation and verification of a flightlog (also referred to below as a “flight log data” or “electronic flightlog”) and squawk list file (also referred to below as a “squawk list”).The disclosed embodiments can be used to automatically populate flightlog and squawk list file for the pilot after the aircraft lands. Thedisclosed embodiments can eliminate the need for the pilot to manually,hand-enter and update data to create/update flight log and squawk listinformation thereby reducing pilot work load post-flight.

The aircraft includes an onboard computer having a processor thatexecutes program modules of an Aircraft Health and Trend Monitoring Unit(AHTMU) throughout the flight to collect data that is used to generate apreliminary flight log file and a preliminary squawk list file.

At a later time, a person (e.g., pilot/maintenance person) can then runa software application that executes on a wireless communication device(WCD), such as a tablet computing device (e.g., an iPad) or smartphone.When the software application runs/executes, it retrieves thepreliminary flight log file and the preliminary squawk list file (thatwas created throughout the flight) over a wireless communication linkthat has been established with the on-board computer. The softwareapplication extracts data from the preliminary flight log file and thepreliminary squawk list file, and populates various fields of agraphical user interface (GUI) that is displayed on a display of theWCD. The GUI presents pertinent data required by the pilot for updatingthe information contained in the preliminary flight log file and thepreliminary squawk list file.

The pilot can then review each squawk event presented on the GUI. Duringthis review process, for each squawk event presented on the GUI, thepilot can use an input/output device of the tablet computer to inputadditional information (if necessary) including new squawk events,change or update information (if necessary) for particular squawkevents, remove/delete particular squawk events, and then eventuallyapprove each squawk event when that squawk event is determined to beacceptable (e.g., accurate or complete or ready for processing).

Once all squawk events from the preliminary flight log file and thepreliminary squawk list file have been presented, reviewed (e.g.,changed or updated) and then approved, the pilot can approve the revisedflight log and squawk list file to generate a final flight log andsquawk list file (e.g., a single .xml file) that has been approved bythe pilot

FIG. 1 is an integrated system 100 for health and trend monitoring of anaircraft 110 and the aircraft's various sub-systems in accordance withsome of the disclosed embodiments. As used herein, the term “healthmonitoring” refers to the process of collecting and evaluating relevantparameters and/or measured data to determine the state, status, ornumerical output value of a component and/or sub-system in any giventime period. As used herein, the term “trend monitoring” refers to theprocess of collecting and evaluating relevant parameters and/or measureddata to determine the state, status, or numerical output value of acomponent and/or sub-system in any given time period in order topredict, estimate, or trend, said state, status, or numerical outputvalue of a component and/or sub-system at a future time.

The system includes an aircraft 110, a WLAN access point 133, a cellularbase station 134, a wireless communication device (WCD) 135, a groundsupport network (GSN) 116, a server 118 and a computer interface 122located at aircraft monitoring center of either an operator or theaircraft manufacturer.

In response to various trigger events or Crew Alerting System (CAS)messages, the aircraft 110 generates and communicates information to theWLAN access point 133 via a WLAN communication link 130 or to a cellularbase station 134 via a cellular communication link 132. The informationcan include, among other things, measured data for relevant variables,CAS messages, and measured data for relevant parameters associated witheach of the relevant variables and CAS messages. The WLAN access point133 or the cellular base station 134 communicates the parameter filesvia a wired link over the Internet 136 to the ground support network116. The ground support network 116 is coupled to the server 118 via acommunication link.

The WCD 135 can be The WCD 135 (also referred to below simply as adevice 135) can be any type of electronics device that is capable ofwireless communication with a network, and includes elements such as atransceiver, computer readable medium, processor, and a display that arenot illustrated since those elements are known in the art. The WCD 135can be, for example, any number of different portable wirelesscommunications devices, such as personal or tablet computers, cellulartelephones, smartphones, etc.

In the embodiment of FIG. 1, the WCD 135 is a smartphone. In thisregard, it is noted that as used herein, a smartphone refers to a mobiletelephone built on a mobile operating system with more advancedcomputing capability and connectivity than a feature phone. In additionto digital voice service, a modern smartphone has the capability ofrunning applications and connecting to the Internet, and can provide auser with access to a variety of additional applications and servicessuch as text messaging, e-mail, Web browsing, still and video cameras,MP3 player and video playback, etc. Many smartphones can typicallyinclude built in applications that can provide web browser functionalitythat can be used display standard web pages as well as mobile-optimizedsites, e-mail functionality, voice recognition, clocks/watches/timers,calculator functionality, personal digital assistant (PDA) functionalityincluding calendar functionality and a contact database, portable mediaplayer functionality, low-end compact digital camera functionality,pocket video camera functionality, navigation functionality (cellular orGPS), etc. In addition to their built-in functions, smartphones arecapable of running an ever growing list of free and paid applicationsthat are too extensive to list comprehensively.

The WCD 135 is WLAN-enabled and Bluetooth-enabled meaning that itincludes for communicating according to either of those specifications.Because the WCD 135 is a portable it can be carried close to theaircraft 110 or far away from the aircraft 110. Depending upon itsproximity to the aircraft 110, the WCD 135 can in some cases establish awireless connection with the wireless communication interfaces 271 whenit is within communication range of the wireless communicationinterfaces 271. For example, in some cases, the WCD 135 can be farenough away from the aircraft 110 such that it is not possible for it toestablish a direct wireless connection to short-range wirelessinterfaces such as Bluetooth or WLAN interfaces that are implemented atthe wireless communication network interface module 271. By contrast, atother times, the WCD 135 can be located close enough to the aircraft 110to establish a wireless connection to the onboard computer 210 over ashort-range wireless communication link. When the WCD 135 is coupled tothe onboard computer 210 via a wireless connection with the wirelesscommunication interfaces 271, the WCD 135 can transmit information tothe onboard computer 210 or receive information from the onboardcomputer 210 as data packets (e.g., as IP packets) via a USB connectionor via a Bluetooth or WLAN link to corresponding interfaces implementedat block 271

The ground support network 116 is operated by a third party. The groundsupport network 116 includes several health management algorithms thatare used to process data included in the parameter files. Once the datafrom the parameter files is processed using the appropriate healthmanagement algorithms, the ground support network 116 generates webpages that are provided to the server 118. The web pages includeinformation regarding aircraft health and/or fleet health. The web pagescan include information stored in parameter files that are communicatedfrom the aircraft 110 to the ground support network 116. The web pagescan also include information stored in inspection files generated at theground support network 116 as well as information that identifieselements of the aircraft, such as sub-systems (or components thereof),which need to be inspected.

The server 118 serves the web pages from the ground support network 116to a computer that is coupled to the computer interface 122 so that theweb pages can be displayed.

The computer interface 122 allows communication to the ground supportnetwork 116, for example from a system operator and/or another computersystem, and can be implemented using any suitable method and apparatus.This way, the information generated at the ground support network 116can be viewed by personnel at a monitoring station on the computerinterface 122 by an operator. The computer interface 122 can include oneor more network interfaces to communicate to other systems orcomponents, one or more terminal interfaces to communicate withtechnicians, and one or more interfaces to connect to the processor116-1 or memory 116-2 of the ground support network 116.

FIG. 2A is a perspective view of an aircraft 110 that can be used inaccordance with some of the disclosed embodiments. In accordance withone non-limiting implementation of the disclosed embodiments, theaircraft 110 includes a fuselage, two main wings 201-1, 201-2, avertical stabilizer 212, an elevator 209 that includes two horizontalstabilizers 213-1 and 213-2 in a T-tail stabilizer configuration, andtwo jet engines 211-1, 211-2. For flight control, the two main wings201-1, 201-2 each have an aileron 202-1, 202-2, an aileron trim tab206-1, 206-2, a spoiler 204-1, 204-2 and a flap 203-1, 203-2, thevertical stabilizer 212 includes a rudder 207, and the aircraft'shorizontal stabilizers (or tail) 213-1, 213-2 each include an elevatortrim tab 208-1, 208-2. Although not shown in FIG. 1, the aircraft 110also includes an onboard computer, aircraft instrumentation and variouscontrol systems as will now be described with reference to FIG. 2B.

FIG. 2B is a block diagram of an Aircraft Health and Trend Monitoring(AHTM) system 200 in accordance with an exemplary implementation of thedisclosed embodiments. Part of the system 200 is implemented within anaircraft 110 for acquiring data. This data can include measured data forone or more relevant variables, measured data for relevant parametersassociated with the one or more relevant variables, CAS messages andmeasured data for relevant parameters associated with the one or moreCAS messages, flight log data, flight log files, squawk events, andsquawk list files. This data can then be communicated from the aircraft110 to the ground support network 116 and used for monitoring the healthof one or more elements (e.g., sub-systems 230 or components of suchsub-systems) of the aircraft 110, and/or for monitoring trendingbehavior exhibited by one ore more elements of the aircraft 110. Asshown, the system 200 includes various sub-systems 230 of the aircraft110.

The aircraft 110 portion of the system 200 includes an onboard computer210, various sub-systems 230, aircraft instrumentation 250, cockpitoutput devices 260 (e.g., display units 262 such as control displayunits, multifunction displays (MFDs), etc., audio elements 264, such asspeakers, etc.), and various input devices 270 such as a keypad whichincludes a cursor controlled device, and one or more touchscreen inputdevices which can be implemented as part of the display units.

The aircraft instrumentation 250 can include, for example, the elementsof a Global Position System (GPS), which provides GPS informationregarding the position and speed of the aircraft, and elements of anInertial Reference System (IRS), proximity sensors, switches, relays,video imagers, etc. In general, the IRS is a self-contained navigationsystem that includes inertial detectors, such as accelerometers, androtation sensors (e.g., gyroscopes) to automatically and continuouslycalculate the aircraft's position, orientation, heading and velocity(direction and speed of movement) without the need for externalreferences once it has been initialized.

The cockpit output devices 260 can include display units 262 and audioelements 264. The display units 262 can be implemented using anyman-machine interface, including but not limited to a screen, a displayor other graphical user interface (UI). The audio elements 264 caninclude speakers and circuitry for driving the speakers.

The input devices 270 can generally include, for example, any switch,selection button, keypad, keyboard, pointing devices (such as a cursorcontrolled device or mouse) and/or touch-based input devices includingtouch screen display(s) which include selection buttons that can beselected using a finger, pen, stylus, etc.

The onboard computer 210 includes a data bus 215, a processor 220,system memory 223, and wireless communication network interfaces 271.

The data bus 215 serves to transmit programs, data, status and otherinformation or signals between the various elements of FIG. 2B. The databus 215 is used to carry information communicated between the processor220, the system memory 223, the various sub-systems 230, aircraftinstrumentation 250, cockpit output devices 260, various input devices270, and wireless communication network interfaces 271. The data bus 215can be implemented using any suitable physical or logical means ofconnecting the on-board computer 210 to at least the external andinternal elements mentioned above. This includes, but is not limited to,direct hard-wired connections, fiber optics, and infrared and wirelessbus technologies.

The processor 220 performs the computation and control functions of thecomputer system 210, and may comprise any type of processor 220 ormultiple processors 220, single integrated circuits such as amicroprocessor, or any suitable number of integrated circuit devicesand/or circuit boards working in cooperation to accomplish the functionsof a processing unit.

It should be understood that the system memory 223 may be a single typeof memory component, or it may be composed of many different types ofmemory components. The system memory 223 can includes non-volatilememory (such as ROM 224, flash memory, etc.), volatile memory (such asRAM 225), or some combination of the two. The RAM 225 can be any type ofsuitable random access memory including the various types of dynamicrandom access memory (DRAM) such as SDRAM, the various types of staticRAM (SRAM). The RAM 225 includes an operating system 226, and flight logand squawk list file generation programs 228. The RAM 225 storesexecutable code for one or more flight log and squawk list filegeneration programs 228. The flight log and squawk list file generationprograms 228 (stored in system memory 223) that can be loaded (viaDirect Memory Access (DMA)) at the processor 220 and executed atprocessor 220 to implement a flight log and squawk list file generationmodule 222 at processor 220.

The processor 220 executes program modules of an Aircraft Health andTrend Monitoring Unit (AHTMU) 221 throughout the flight to collect data.As will be explained below, the processor 220 executes the flight logand squawk list file generation programs 228 and uses the data collectedby the AHTMU 221 to generate a preliminary flight log file and apreliminary squawk list file that can be used at a wirelesscommunication device to generate a final flight log and a final squawklist file that can then be provided to the ground support network 116and used for conducting health and trend monitoring for one or moreaircraft sub-systems (or components thereof).

As used herein, a “flight log” can refer to a record of each flight thatincludes information such as date of the flight, flight leg, pilot name,co-pilot name, origin airport, destination airport, block-in time andblock-out time, takeoff time, landing time, indication of whether it wasa day flight or a night flight, fuel burned, engine cycles, APU cycles,etc.

As used herein, a “squawk list” can refer to a list of squawk eventsthat are recorded during a specific flight. Squawk events generallyrequire a corrective action within a certain time period, depending onthe severity of the particular squawk event. A squawk event can beeither a discrepancy or an event related to a CAS message (CAS messagesare described in detail above). A discrepancy can be any issue arisingon an aircraft that requires corrective action. A discrepancy refers toany type of squawk event that is not related to a CAS message, anddiffers from a CAS message in that discrepancies can be manually enteredinto the squawk list by a person, such as a pilot or maintenancepersonnel, either pre-flight before takeoff, during flight orpost-flight after the aircraft has landed during a time period betweenlanding and a final approval of the squawk list. By contrast, CASmessages are automatically generated during flight and added to thesquawk list without human intervention.

The processor 220 is also used to implement a server module 227 that issometimes referred to as a cabin server. As will be described below withreference to FIG. 4, the server module 227 can provide information(including the preliminary flight log file and a preliminary squawk listfile) to external computers and devices, and can receive informationfrom external computers and devices.

In addition, it is noted that in some embodiments, the system memory 223and the processor 220 may be distributed across several differenton-board computers that collectively comprise the on-board computersystem 210.

The wireless communication network interfaces 271 are operatively andcommunicatively coupled antennas 272, 274, 276 that are external to theon-board computer 210. The antennas include a satellite antenna 272 thatcan be used to communicate information with a satellite gateway 114 overa satellite communication link, a WLAN antenna 274 that can be used tocommunicate information with a WLAN access point 133 over a WLANcommunication link, and a cellular network antenna 276 that can be usedto communicate information to/from a cellular base station 134 over acellular communication link. The satellite gateway 114, the WLAN accesspoint 133, and the cellular base station 134 can all be coupled to othernetworks, including the Internet, so that information can be exchangedwith remote computers.

FIG. 2C is a block diagram of various sub-systems 230 of an aircraft 110in accordance with an exemplary implementation of the disclosedembodiments. In one exemplary, non-limiting implementation, the varioussub-system(s) 231-246 include a thrust reverser control sub-system(s)231, a brake control sub-system(s) 232, a flight control sub-system(s)233, a steering control sub-system(s) 234, aircraft sensor controlsub-system(s) 235, an APU inlet door control sub-system(s) 236, a cabinenvironment control sub-system(s) 237, a landing gear controlsub-system(s) 238, propulsion sub-system(s) 239, fuel controlsub-system(s) 240, lubrication sub-system(s) 241, ground proximitymonitoring sub-system(s) 242, aircraft actuator sub-system(s) 243,airframe sub-system(s) 244, avionics sub-system(s) 245, softwaresub-system(s) 246. The sub-system(s) 230-246 that are illustrated inFIG. 2B are exemplary only, and in other embodiments various othersub-system(s) can be included such as, for example, air datasub-system(s), auto flight sub-system(s), engine/powerplant/ignitionsub-system(s), electrical power sub-system(s), communicationssub-system(s), fire protection sub-system(s), hydraulic powersub-system(s), ice and rain protection sub-system(s), navigationsub-system(s), oxygen sub-system(s), pneumatic sub-system(s),information sub-system(s), exhaust sub-system(s), etc.

Although not illustrated in FIG. 2C, those skilled in the art willappreciate that each of the various sub-systems can include one or morecomponents. In addition, each of the various sub-systems can eachinclude one or more sensors to facilitate measurement and generation ofdata pertaining to operation of that sub-system of the aircraft 110(and/or a component of that sub-system), to assist in performingdiagnostics and health monitoring of one or more sub-systems, etc. Eachsensor can generate data that is used to generate information that canbe included in squawk list files that are generated by the flight logand squawk list file generation module 222. In general, a “sensor” is adevice that measures a physical quantity and converts it into a signalwhich can be read by an observer or by an instrument. In general,sensors can be used to sense light, motion, temperature, magneticfields, gravitational forces, humidity, vibration, pressure, electricalfields, current, voltage, sound, and other physical aspects of anenvironment. Non-limiting examples of sensors can include acousticsensors (e.g., sound, microphone, seismometer, accelerometer, etc.),vibration sensors, vehicle sensors (e.g., air speed indicator,altimeter, attitude indicator, gyroscope, inertial reference unit,magnetic compass, navigation instrument sensor, speed sensors, throttleposition sensor, variable reluctance sensor, viscometer, wheel speedsensor, Yaw rate sensor, etc.), chemical sensors/detectors, electriccurrent sensors, electric potential sensors, magnetic sensors, radiofrequency sensors, environmental sensors, fluid flow sensors, position,angle, displacement, distance, speed, acceleration sensors (e.g.,accelerometer, inclinometer, position sensor, rotary encoder,rotary/linear variable differential transformer, tachometer, etc.),optical, light, imaging sensors (e.g., charge-coupled device, infra-redsensor, LED, fiber optic sensors, photodiode, phototransistors,photoelectric sensor, etc.), pressure sensors and gauges, strain gauges,torque sensors, force sensors piezoelectric sensors, density sensors,level sensors, thermal, heat, temperature sensors (e.g., heat fluxsensor, thermometer, resistance-based temperature detector, thermistor,thermocouple, etc.), proximity/presence sensors, etc.

FIG. 3 is a block diagram of portions of a Ground support network (GSN)116 in accordance with one exemplary implementation of the disclosedembodiments. As illustrated in FIG. 3, the ground support network 116includes a processor 290, memory 292 and communication interfaces 293that are coupled to various different wired communication links.

The memory 292 can be implemented using any of the memory technologiesthat are disclosed herein. The memory 292 stores a plurality of AircraftHealth and Trend Monitoring (AHTM) program modules 293-1 . . . 293-n.Each of the AHTM program modules 293 are programmed with computerexecutable instructions for implementing a particular health and trendmonitoring algorithm (HTMA). The memory 292 can store various differentAHTM program modules 293 that can be used to implement various differentHTMAs via computer executable instructions.

When parameter files 291-1 . . . 291-n are received at the groundsupport network 116 from the aircraft 110, each parameter file 291 canbe loaded at the processor 290 along with a corresponding AHTM programmodule 293 that corresponds to that particular type of parameter file.When the processor 290 executes the computer executable code of an AHTMprogram module 293 with respect to measured data included in one of theparameter files 291, an instantiation of an Aircraft Health and TrendMonitoring (AHTM) processor 294 is implemented at the processor 290.

Relevant Variable Embodiments

In accordance with some of the disclosed embodiments, each HTMA is usedto analyze measured data for at least one relevant variable (RV) todetermine whether the measured data is abnormal (i.e., outside of itsupper and/or lower threshold limits) or normal (i.e., within its upperand/or lower threshold limits).

In accordance with these embodiments, when a parameter file 291 isreceived and loaded at the processor 290 of the ground support network116, the processor 290 determines which relevant variables are includedin the parameter file 291. For each relevant variable, the processor 290loads and executes an appropriate AHTM program module 290 (thatcorresponds to the particular relevant variable). For each AHTM programmodule 290 and parameter file 291, an HTMA then analyzes the measureddata for that relevant variable (RV) to determine whether that relevantvariable is at an abnormal level (i.e., outside of its upper and/orlower threshold limits). If the measured data for that relevant variableis determined to be abnormal, the HTMA can flag the abnormality and thenalso further examine measured data for relevant parameters (RPs) thatare associated with that particular relevant variable to determine whichrelevant parameters are most likely causing the relevant variable to beat an abnormal level.

To explain further, each HTMA has at least one relevant variable (RV)associated with it that is used during initial analysis of a particularsub-system of an aircraft or of a component of a particular sub-system.Each relevant variable is influenced or affected by a number ofdifferent relevant parameters (RPs). Each of the relevant parameters arealso associated with the particular sub-system or component of theaircraft, and help characterize the performance or operationalcharacteristics of that particular sub-system or component. For aparticular HTMA, the relevant variables and the relevant parameters foreach relevant variable, as well as thresholds (e.g., upper and/or lowerthresholds) for each relevant variable and each of its relevantparameters, are pre-defined.

When a relevant variable is determined to be abnormal during executionof a particular HTMA, measured data for each of the relevant parameterscorresponding to that relevant variable can then be compared to one ormore thresholds, and any relevant parameters that are determined to beoutside their respective threshold(s) can then be identified as being apotential cause of the abnormal relevant variable and can then be storedin an inspection file 296. In some implementations, the inspection file296 can also indicate particular sub-system(s) (or components thereof)that each of the relevant parameters are associated with. This way,those particular sub-system(s) (or components thereof) can be easilyidentified for further inspection to determine whether they areoperating correctly or whether corrective actions need to be taken.

CAS Message Embodiments

Many modern aircraft used Crew Alerting System (CAS) messages to provideengine and aircraft system fault information to the crew. CAS messagesare annunciated to the crew based on triggers and logic embedded in theavionics suite. The logic typically contains inputs from all reportingaircraft systems and sub-systems. A CAS message is triggered when thecombination of inputs meets the criteria of embedded logic. This couldbe Boolean or binary type inputs, or floating point parameters. Once thelogic has been satisfied, the avionics suite displays a message to thecrew in either Red (warning), Amber (caution), or Cyan (advisory). ManyCAS messages display failure or fault information to the crew. In theseinstances when failure or fault information is displayed, it is assumedthat the system has experienced an anomaly and a corrective action mustbe performed to successfully extinguish the CAS message. The system isrecords all of the CAS parameters at any given time. The CAS parametervalue of the message is 0 until the CAS message becomes active. Onceactive, the value of the CAS parameter value changes from zero to aninteger between one (1) and sixty-three (63) depending on what failed.As the CAS messages are recorded, the system is detects when the valueof the parameter changes from zero to a non-zero value.

In accordance with some of the other disclosed embodiments, when a CASmessage is generated on-board the aircraft 110, the data for relevantparameters (RPs) that are associated with that particular CAS messageare automatically measured and stored in a parameter file 291 that istransmitted to the ground support network 116. Aircraft maintenance andengineering personnel can determine based on experience a number ofdifferent relevant parameters (RPs) that are the typical triggers foreach particular CAS message. As such, for each particular CAS message,relevant parameters and their respective thresholds (e.g., upper and/orlower thresholds for each relevant parameter) can be pre-defined.

When a parameter file 291 is received and loaded at the processor 290 ofthe ground support network 116, the processor 290 also loads andexecutes an appropriate AHTM program module 293 (that corresponds to theparticular CAS message indicated in the parameter file 291). When theprocessor 290 executes the HTMA that corresponds to the AHTM programmodule 293, the measured data for each of the relevant parameters (RPs)that are included in the parameter file 291 are analyzed to determinewhich of the relevant parameters are at an abnormal level (i.e., outsideof its upper and/or lower threshold limits) and thus most likely causingthat particular CAS message to be generated. Each of the relevantparameters can be compared to one or more thresholds, and any relevantparameters that are determined to be outside those threshold(s) can beidentified as being a potential cause of the CAS message. When themeasured data for any relevant parameter is determined to be abnormal,the HTMA can flag the abnormality and the relevant parameters that areoutside of their respective threshold(s) can then be stored in aninspection file 296. In some implementations, the inspection file 296can also indicate particular sub-system(s) (or components thereof) thateach of the relevant parameters are associated with. This way, thoseparticular sub-system(s) (or components thereof) can be identified andflagged for further inspection to determine whether they are operatingcorrectly or whether corrective actions need to be taken.

Automated Generation and Verification of a Flight Log and Squawk ListFile

The disclosed embodiments relate to methods, systems and computerprogram products for automated generation and verification of a flightlog (also referred to below as a “flight log data” or “electronic flightlog”) and squawk list file (also referred to below as a “squawk list”).The disclosed embodiments can be used to automatically populate flightlog and squawk list file for the pilot after the aircraft 110 lands. Thedisclosed embodiments can eliminate the need for the pilot to manually,hand-enter and update data to create/update flight log and squawk listinformation thereby reducing pilot work load post flight.

FIG. 4 is a method 400 in accordance with some of the disclosedembodiments. FIG. 4 will be described with reference to FIGS. 1-3. As apreliminary matter, it should be understood that the method 400describes interaction between an on-board computer (e.g., 220 of FIG.2B) at the aircraft and a wireless communication device 135 as a user ofan application interacts with the application to generate of a finalflight log and a final squawk list. The various tasks performed inconnection with method 400 may be performed by software, hardware,firmware, or any combination thereof. In certain embodiments, some orall steps/tasks/acts of this process, and/or substantially equivalentsteps/tasks/acts, are performed by execution of processor-readableinstructions stored or included on a non-transitory processor-readablemedium. For instance, references to a processor performing functions ofthe present disclosure refer to any one or more interworking computingcomponents executing instructions, such as in the form of an algorithm,provided on at least one non-transitory processor-readable medium, suchas a memory as described herein. For illustrative purposes, thefollowing description of method 400 may refer to elements mentionedabove in connection with FIGS. 1-3. In practice, portions of method 400may be performed by different elements of the described system, e.g.,component A, component B, or component C. In addition, it should beunderstood that steps/tasks/acts of the method 400 are not necessarilypresented in any particular order and that performance of some or allthe steps/tasks/acts in an alternative order is possible and iscontemplated. The steps/tasks/acts have been presented in thedemonstrated order for ease of description and illustration. Further,steps/tasks/acts can be added, omitted, and/or performed simultaneouslywithout departing from the scope of the appended claims. As such, itshould be appreciated that method 400 may include any number ofadditional or alternative tasks, the tasks shown in FIG. 4 need not beperformed in the illustrated order, and method 400 may be incorporatedinto a more comprehensive procedure or process having additionalfunctionality not described in detail herein. Moreover, one or more ofthe tasks shown in FIG. 4 could be omitted from an embodiment of themethod 400 as long as the intended overall functionality remains intact.It should also be understood that the illustrated method 400 can end atany time.

It is noted that prior to the start of method 400, an on-board computer(e.g., an AHTMU 221) at the aircraft records flight log data for aflight in a preliminary flight log data file. This flight log data canbe recorded, prior to flight, while the aircraft is in flight, and/orafter the aircraft lands. The flight log can include flightidentification information and flight data information. The flightidentification information identifies information about the flight suchas the date of the flight, flight leg, pilot name, co-pilot name, originairport, destination airport, block-in time and block-out time, takeofftime, landing time, indication of whether the flight was a day flight ora night flight, etc. By contrast, flight data information is specificaircraft system data that is recorded before, during, or after theflight. Flight data information can indicate information regarding astate, a value, or a current cycle of any aircraft systems orsub-system. Examples of flight data information can include things suchas amount of fuel burned, number of engine cycles, number of APU cycles,number of landing gear cycles, number of thrust reverser cycles, etc.

In addition, while the aircraft is in flight, the on-board computer(e.g., the AHTMU 221) at the aircraft automatically collects and recordssquawk events that occur (or are entered by the pilot or crew) in a“preliminary” squawk list file for that flight. The preliminary squawklist file includes a list of squawk events that are recorded during theflight. Each squawk event can be an event that can be detected, measuredor observed during the flight. Items that are approved for inclusion inthe final squawk list are those squawk events that are flagged to beinvestigated for a corrective action after the flight.

Examples of squawk events can include either discrepancies or eventsrelated to or associated with CAS messages. A discrepancy is an squawkevent that is observed by a human and manually entered into thepreliminary squawk list file by the human either pre-flight beforetakeoff, during the flight, or post-flight after the aircraft haslanded. The discrepancy, once approved, is flagged to be investigatedfor a corrective action after the flight. By contrast, an event relatedto a CAS message is a squawk event that is automatically generatedduring flight and added to the preliminary squawk list file withouthuman intervention. An event related to the CAS message can be detected,measured or observed during the flight. When approved by a user, thatevent is flagged to be investigated for a corrective action after theflight.

The method 400 begins at 405, when a trigger event occurs, and anon-board computer (e.g., an AHTMU 221) at the aircraft automaticallygenerates a preliminary squawk list file that comprises a plurality ofsquawk events to be reviewed for potential inclusion in a final squawklist. In one implementation, the trigger event at 405 can be, forexample, when the aircraft 110 lands and/or other trigger events occurto indicate that the aircraft 110 is on the ground (e.g., when anindication is received that an engine of the aircraft has been turnedoff, a door has opened or any other indication that the aircraft is onthe ground). In one embodiment, the AHTMU 221 can then execute theflight log and squawk list file generation module 222 to generate apreliminary flight log data file and a preliminary squawk list file thatincludes a plurality of squawk events to be reviewed for potentialinclusion in a final squawk list. The AHTMU 221 transfers thepreliminary flight log data file and the preliminary squawk list file toan onboard cabin server 227 that is also implemented at the onboardcomputer 210. The onboard cabin server 227 can then directly orindirectly communicate this information to the wireless communicationdevice 135.

At 410, a user (e.g., pilot/maintenance person) of the wirelesscommunication device 135 makes an input (e.g., presses a buttondisplayed on the graphical user interface of a tablet computing device,such as, an iPad or smartphone), to execute a software application thatis designed to generate the final flight log and the final squawk listfile.

When the software application is started, the software applicationcauses the wireless communication device to establish a wirelessconnection with an on-board computer of the aircraft (at 412). Forexample, in one embodiment, when the software application beginsexecuting, at 412, the wireless communication device 135 communicatesthe on-board computer 210 to establish a connection to the cabin server227 via one of the wireless communication network interfaces. Thewireless communication link can be, for example, a short-range wirelesscommunication link such as a Wireless Local Area Network (WLAN) link orBluetooth link or a loner-range wireless communication link such as acellular link.

Once the connection is established, at 414, the wireless communicationdevice 135 receives the preliminary flight log data file and thepreliminary squawk list file from the cabin server 227. For example, inone embodiment, the software application at the wireless communicationdevice 135 can communicate a request to the cabin server 227 to requestthe preliminary flight log data file and the preliminary squawk listfile (that was created throughout the flight by the AHTMU 221) from thecabin server 227 over the wireless communication link that has beenestablished with an onboard computer 210 of the aircraft 110. Inresponse to the request message communicated from the wirelesscommunication device, the cabin server 227 communicates the preliminaryflight log data file and the preliminary squawk list file to thewireless communication device. In an alternative implementation, thecabin server 227 can automatically push the preliminary flight log datafile and the preliminary squawk list file to the wireless communicationdevice 135 once the wireless communication connection has been establishwith the wireless communication device 135.

At 416, the software application at the wireless communication device135 extracts information from the preliminary flight log data file andinformation associated with each squawk event from the preliminarysquawk list file, and populates various fields of a graphical userinterface (UI), that is displayed on a display of the wirelesscommunication device, with information from the preliminary flight logdata file and with information associated with each squawk event fromthe preliminary squawk list file. As will be describe below withreference to FIG. 5, the GUI can be used to present pertinent data fromthe preliminary flight log file and the preliminary squawk list file forreview, updating and approval.

At 420, each squawk event from the preliminary squawk list file can bepresented via the graphical user interface of wireless communicationdevice for review and approval by the user (e.g., pilot or otherperson). Using the graphical user interface of wireless communicationdevice, the user can review each squawk event in the preliminary squawklist for approval and inclusion in a final squawk list. For example, auser can then review each squawk event presented on the GUI of thewireless communication device 135, and for each squawk event presentedon the GUI, the user can use an input/output device of the tabletcomputer to input additional information (if necessary), change orupdate information (if necessary). The user can use the input/outputsystem to input information to either: approve the squawk event,remove/delete the squawk event, or edit the content of the squawk event.In this regard, for a particular squawk event in the preliminary squawklist, the user can input (1) an edit input to change content of thatparticular squawk event, (2) an approval input that indicates that theparticular squawk event has been approved for inclusion in the finalsquawk list, or (3) a removal input that indicates that the particularsquawk event has not been approved for inclusion in the final squawklist and is to be deleted/removed from the preliminary squawk list. Insome embodiments, while reviewing the squawk events from the preliminarysquawk list file, the user can also be presented with the option to addor input new squawk events by entering new information or making an“addition” input. Items that are approved are included in the finalsquawk list.

In one embodiment of 420, at 422, the next squawk event from thepreliminary squawk list file can be presented via the graphical userinterface for review and approval by the user. In one implementation ofstep 420, at 422, the user is presented with and reviews a “next” squawkevent on the GUI of the wireless communication device 135 along with anoption to approve that squawk event. The user can approve the squawkevent with no changes, edit the squawk event before approving it (e.g.,change information associated with that squawk event and/or enter newinformation for that squawk event), or reject the squawk event entirely.For example, when the squawk event is incomplete or inaccurate the usercan edit prior to approving the squawk event. The user approves when theuser determines that it is acceptable (accurate or complete) and infinal approved form. When a squawk event is approved at 424 then thatsquawk event is included in the final squawk list, and the method 400proceeds to 426. When appropriate, the user can edit the content of thesquawk event prior to approving it. When a squawk event is not approvedand is to be removed/deleted, at 425 that squawk event can be removedfrom the preliminary squawk list and the method proceeds to 426.

At 426, the software application checks to determine whether all squawkevents have been reviewed. When all squawk events have not yet beenreviewed the method 400 loops to 422. When the software applicationdetermines (at 426) that all squawk events in the preliminary squawklist have been reviewed (e.g., all squawk events have been presented,reviewed (e.g., changed or updated), approved or deleted), the method400 proceeds to 430.

At 430, the software application queries the user to determine whetherthe squawk list and flight log data files are approved (e.g., bypresenting a question to the user that requires the user to input anindication that the files have been approved and is in final form), andif so, the method then proceeds to step 440. By contrast, if the squawklist and flight log data files are not approved (e.g., the user inputsan indication that the files have not been approved and are not yet infinal form), then the method loops back to 420 where the user continuesto edit one or more squawk events in the squawk list and flight log datafiles prior to the final flight log and final squawk list file beinggenerated at 440.

At 440, the software application at the wireless communication device135 generates a final flight log and a final squawk list file (e.g., asingle .xml file) that has been approved by the user. The final flightlog includes the flight log data that was recorded (and possibly editedduring review) and approved for inclusion in the final flight log. Thefinal squawk list file includes each of the squawk events from thepreliminary squawk list that have been reviewed (and possibly edited)and approved for inclusion in the final squawk list.

The final flight log and the final squawk list file can then becommunicated from the wireless communication device to other computersof the integrated system 100 of FIG. 1.

For example in one embodiment illustrated in FIG. 4, the wirelesscommunication device can communicate the final flight log and the finalsquawk list file over a wireless communication link to the cabin server227 (via one of the interfaces 271). The cabin server 227 can thencommunicate this information to the AHTMU 221.

At 450, the AHTMU 221 can communicate the final flight log and the finalsquawk list file from the aircraft (via one of the interfaces 271 ofFIG. 2B) to the ground support network (GSN) 116.

At 460, the GSN 116 can communicate the final flight log and the finalsquawk list file to the maintenance server 118 that executes one or moreprogram modules to automatically upload and import the final flight logand the final squawk list file into records associated with theaircraft. The server 118 can be associated with a maintenance trackingsoftware program that is part of a Computerized Maintenance Program(CMP).

The method then ends at 470.

FIG. 5 is a block diagram that illustrates a wireless communicationdevice in accordance with the disclosed embodiments. Depending on theimplementation, the wireless communication device 535 may be, forexample but not by way of limitation, a cellular telephone (or“smartphone”), a computer (e.g., a tablet, a laptop, a notebook, orother computer), or any other network-enabled communication and/orcomputing device.

The wireless communication device 535 can include a processor orprocessing system 522, one or more network interfaces 524, a memory 526that stores the software application (described above with respect toFIG. 4), and a user interface 530 that includes elements of aninput/output system such as a keypad 532, an audio output device 534,touchscreen 536, a display 538, etc. The processing system 522 iscoupled to one or more network interfaces 524, memory 526, and userinterface circuitry 530.

Processing system 522 provides information to network interface 524 fortransmission to the on-board computer 210 of the aircraft 110 eitherdirectly or indirectly over a network (e.g., a cellular network, localarea network or other radio network not illustrated in FIG. 5). Theprocessing system 522 receives information from network interface 524,which includes information transmitted by the on-board computer 210 ofthe aircraft 110 to wireless communication device 535 either directly orover a network.

Network interface 524 may include an antenna for receiving andtransmitting radio frequency (RF) signals, receiver circuitry,transmitter circuitry, and circuitry to couple the antenna to thereceiver circuitry and transmitter circuitry in a manner familiar tothose skilled in the art. In an embodiment in which wirelesscommunication device 535 interfaces with a wired network (e.g., a LAN,WAN, or other wired network), network interface 524 may include anetwork interface controller, network interface card or network adapter(e.g., a LAN or WAN adapter).

Memory 526 is configured to store information received from processingsystem 522 and to provide information to processing system 522. Thisinformation may include application software (e.g., the softwareapplication described above with reference to FIG. 3). In addition,memory 526 can also store the preliminary flight log, the preliminarysquawk list file, the final flight log and the final squawk list file.Memory 526 can be implemented using any of the memory technologiesdescribed above with reference to FIG. 2B.

User interface circuitry 530 includes a plurality of devices adapted toreceive information from a user of the wireless communication device 535and/or to convey information (e.g., visual, audible, or tangibleinformation) to the user. User interface circuitry 530 may include, forexample, a keypad 532, one or more audio output devices 534, and both oreither a touchscreen 536 and/or a display device 538. In addition, userinterface circuitry 530 may include various other devices (e.g., amicrophone and/or haptic device (e.g., a vibrator)), not shown. Keypad532 and touchscreen 536 are configured to receive typed inputs from auser of wireless communication device 535, which inputs may includetext, spaces, carriage returns, symbols, and control or text selectioninputs (e.g., backspaces, deletions, text highlights, and so on). Thekeypad 532 can be implemented as part of the touchscreen 536.

Audio output device 534 may include one or more speakers for providingaudio output to the user, which outputs may include speech, tones,clicks, ringtones, and other audible sounds

Display device 538 and/or touchscreen 536 are configured to presentvideo output to a the user, such as text being generated by the userthrough manipulation of the keypad 532 and information conveyed to thewireless communication device 535. Some non-limiting examples ofscreenshots of the graphical user interface (GUI) that may be producedby display device 538 are illustrated in FIGS. 6 through 12, which willnow be described in greater detail.

Example Graphical User Interface (GUI)

FIGS. 6-12 are examples screens that can be displayed as part of agraphical user interface (GUI) that can be displayed at the wirelesscommunication device 135 in accordance with the disclosed embodiments.This GUI illustrates a flight log page that includes certain flight logdata for a flight (KLBB to KSAV) from a preliminary flight log datafile. This page includes an aircraft registration number identifier 601,a column that includes a list of available flight logs 602, where eachflight log in that column includes information about the departureairport, the arrival airport, the flight date, the block out time foreach flight log, the number of squawk events related to CAS messages,and the number of squawk events that are manually-entered discrepancies.In this example, the first flight log is selected, and specifies KLBB asthe Origination Airport Code of the departure airport, KSAV as theDestination Airport Code of the arrival airport, 26 Jul. 2012 as theflight date, 15:02 as the block out time, thirty-three (33) as thenumber of squawk events related to CAS messages, and zero (0) the numberof squawk events that are manually-entered discrepancies. In addition,the page includes a Flight Log header 603.

Heading 608 indicates the Flight Log Status (Approved/Unapproved).Section 609 specifies various Flight Log Details about: (1) the aircraft(type, serial number, registration number), (2) the flight (includingleg, departure date, departure airport, block out time, flight on time,starting fuel weight, APU hours, arrival date, arrival airport, flightoff time, block in time, and ending fuel weight), and (3) the personnel(including the Captain, first officer, crew, and number of passengers).In some embodiments, any suspect data can appear in white text on black“negative” background (here the starting fuel and ending fuel amountsare shown this way). The page also includes a Home Button 610, a flightlog button 611, and information 612 about the number of squawk eventsincluding the number of different types of CAS messages (e.g.,Warnings=0, Caution=12, Advisory=21 and Info=0) and the number ofmanually-entered discrepancies, which is zero (0) in this example. Thisis an exemplary embodiment only and other sections could be includedsuch as a remarks section, etc.

In general, each screen that is displayed as the graphical userinterface of the wireless communication device (e.g., at 420 and 430 ofFIG. 4) will have various buttons that can be used to select informationor pages or items that they want to view, and various editable fieldsthat are populated with information that can be edited.

For instance, in this particular example, the user can use button 604 toselect and view CAS messages for the selected Flight Log. After the userselects the desired flight log by tapping on it in the list of availableflight logs 602 column, the user can tap the CAS messages button 604,and view a list of CAS messages as shown in FIG. 8. In oneimplementation, the CAS messages will be ordered by their relativepriority and can each be color coded to reflect the type of type of CASmessage (e.g., Warnings=0, Caution=12, Advisory=21 and Info=0). In someembodiments, when a user wants to approve a particular CAS message forinclusion in the final squawk list file, the user can tap upon the CASmessage to mark it with a checkmark (and thus flag it as an item ofimportance and approve it for inclusion in the final squawk list file).Tapping the flight log button (at the top of FIG. 8) will return theuser to the flight log details page (FIG. 6). Alternatively the usercould tap a different entry in the list of available flight logs 602column to return to the flight log details page (FIG. 6).

When a user taps a discrepancies button, additional buttons will bedisplayed on the UI that give the user options to view (and optionallyedit) an existing discrepancy; add a new discrepancy; or delete anexisting discrepancy. When the user selects view an existingdiscrepancy, the user can view that particular discrepancy and then hasthe option to edit/delete/approve that discrepancy.

In this embodiment, the user can use button 605 to select and viewdiscrepancies (if any) for the selected Flight Log. When the user tapsthe discrepancies button 605, a list of any discrepancies will bedisplayed as shown in FIG. 9, where there is only one discrepancy listedfor sake of this particular example. As shown by the arrow in FIG. 9,the user can tap anywhere on the discrepancy to enable editing of thediscrepancy. In addition, an additional button can be displayed thatallows the user to delete the discrepancy if desired. When the userselects edit a discrepancy, they user can be given options as shown inFIG. 11. The user can then select the issue with the relevant category(e.g., the System, Subsystem, Component, etc.), by tapping theassociated “Select” indicator (to the far right in FIG. 11) for thecategory that needs to be edited to bring up a list of items for thatcategory, and the user can select an item from that list. The user doesnot need to change every field in FIG. 11 when the user is editing adiscrepancy. After selecting the desired fields and items in the listassociated with that field, the user can optionally enter remarks in theremarks section, and push the save button to save that discrepancy oncethey are finished. A message will then appear indicating whether thesave operation was successful. That particular discrepancy will be addedto the final squawk list file.

As shown in FIG. 10, when there are no existing discrepancies,additional buttons will appear that allow the user to add a discrepancy,or tap the no discrepancies button to return to the flight log detailspage (FIG. 6). When the user selects add a discrepancy, they user canthen be given options as shown in FIG. 11. The user can then select theappropriate item within each category (e.g., the System, Subsystem,Component, etc.) by tapping the associated “Select” indicator (to thefar right in FIG. 11) to bring up a list of items for each category. Theuser can then select an item from each list and fill in appropriateinformation. After selecting an item in each list, the user canoptionally enter remarks in the remarks section, and push the savebutton to save that discrepancy.

Referring again to FIG. 6, the user can use button 606 to edit theselected Flight Log. For instance, in one implementation, when the usertaps the edit button 606, a virtual keyboard will appear on the GUI asshown in FIG. 7, and the user can select any field within the Flight LogData Section and edit that field (e.g., change values) using the virtualkeyboard. The user can then tap a save changes button to save thechanges, or can tap a cancel edit button to cancel out of the editingmode.

Once the user has viewed and approved all CAS messages anddiscrepancies, the user can use button 607 (of FIG. 6) to approve theselected Flight Log as shown in FIG. 12, and a check mark will appearnext to the approved flight log. At this point, the heading 608 thatindicates the Flight Log Status will indicate that is approved.Additional buttons can then be displayed that allow the user to uploadthe approved flight log(s) to the aircraft.

Those of skill in the art would further appreciate that the variousillustrative logical blocks/tasks/steps, modules, circuits, andalgorithm steps described in connection with the embodiments disclosedherein may be implemented as electronic hardware, computer software, orcombinations of both. Some of the embodiments and implementations aredescribed above in terms of functional and/or logical block components(or modules) and various processing steps. However, it should beappreciated that such block components (or modules) may be realized byany number of hardware, software, and/or firmware components configuredto perform the specified functions. To clearly illustrate thisinterchangeability of hardware and software, various illustrativecomponents, blocks, modules, circuits, and steps have been describedabove generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled artisans may implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the present invention. For example, an embodiment of a systemor a component may employ various integrated circuit components, e.g.,memory elements, digital signal processing elements, logic elements,look-up tables, or the like, which may carry out a variety of functionsunder the control of one or more microprocessors or other controldevices. In addition, those skilled in the art will appreciate thatembodiments described herein are merely exemplary implementations.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a general purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration. The word “exemplary” is used exclusively herein to mean“serving as an example, instance, or illustration.” Any embodimentdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other embodiments.

The steps of a method or algorithm described in connection with theembodiments disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium is coupled to the processor such the processorcan read information from, and write information to, the storage medium.In the alternative, the storage medium may be integral to the processor.The processor and the storage medium may reside in an ASIC.

In this document, relational terms such as first and second, and thelike may be used solely to distinguish one entity or action from anotherentity or action without necessarily requiring or implying any actualsuch relationship or order between such entities or actions. Numericalordinals such as “first,” “second,” “third,” etc. simply denotedifferent singles of a plurality and do not imply any order or sequenceunless specifically defined by the claim language. The sequence of thetext in any of the claims does not imply that process steps must beperformed in a temporal or logical order according to such sequenceunless it is specifically defined by the language of the claim. Theprocess steps may be interchanged in any order without departing fromthe scope of the invention as long as such an interchange does notcontradict the claim language and is not logically nonsensical.

Furthermore, depending on the context, words such as “connect” or“coupled to” used in describing a relationship between differentelements do not imply that a direct physical connection must be madebetween these elements. For example, two elements may be connected toeach other physically, electronically, logically, or in any othermanner, through one or more additional elements.

While at least one exemplary embodiment has been presented in theforegoing detailed description, it should be appreciated that a vastnumber of variations exist. It should also be appreciated that theexemplary embodiment or exemplary embodiments are only examples, and arenot intended to limit the scope, applicability, or configuration of theinvention in any way. Rather, the foregoing detailed description willprovide those skilled in the art with a convenient road map forimplementing the exemplary embodiment or exemplary embodiments. Itshould be understood that various changes can be made in the functionand arrangement of elements without departing from the scope of theinvention as set forth in the appended claims and the legal equivalentsthereof.

What is claimed is:
 1. A method, comprising: recording preliminarysquawk events that occur while an aircraft is in flight; presenting, ata portable device, the preliminary squawk events; receiving approvalinputs that indicate approved squawk events of the preliminary squawkevents; and generating a squawk list that includes each of the approvedsquawk events to be investigated for corrective action after the flight.2. The method of claim 1, further comprising receiving an edit input tochange content of one of the preliminary squawk events.
 3. The method ofclaim 1, further comprising receiving a removal input indicating aremoved squawk event of the preliminary squawk events that is not to beincluded in the squawk list.
 4. The method of claim 1, whereinpresenting the preliminary squawk events includes presenting flight logdata and information associated with each of the preliminary squawkevent.
 5. The method of claim 1, further comprising: in response to arequest message communicated from the portable wireless communicationdevice, communicating the preliminary squawk events from the aircraft tothe portable device.
 6. The method of claim 1, wherein each of thepreliminary squawk events is either: a discrepancy that is observed by ahuman and manually entered by the human, wherein the discrepancy isflagged to be investigated for the corrective action after the flight;or added by an aircraft computer in response to a Crew Alerting System(CAS) message.
 7. The method of claim 1, further comprising: recordingflight log data for the flight; and generating a final flight log basedon the flight log data after the flight.
 8. The method of claim 7,wherein the final flight log comprises: flight identificationinformation for the flight that identifies one or more of: date of theflight, flight leg, pilot name, co-pilot name, origin airport,destination airport, block-in time and block-out time, takeoff time,landing time, indication of whether the flight was a day flight or anight flight; and flight data information that indicates informationregarding a state, a value, or a current cycle of any aircraft systemsor sub-system.
 9. The method of claim 7, further comprising:communicating the final flight log and the squawk list from the portablewireless communication device to a maintenance server.
 10. The method ofclaim 9, wherein communicating the final flight log and the squawk listfrom the portable device to the maintenance server comprises:communicating the final flight log and the squawk list from the portabledevice to an on-board computer of the aircraft; communicating the finalflight log and the squawk list from the on-board computer of theaircraft to a ground support network; and communicating the final flightlog and the squawk list from the ground support network to themaintenance server, wherein the maintenance server automatically uploadsand imports the final flight log and the squawk list into recordsassociated with the aircraft.
 11. A system, comprising: an on-boardcomputer for an aircraft, the on-board computer configured to recordpreliminary squawk events that occur while the aircraft is in flight forpotential corrective action; and a portable device configured tocommunicate with the on-board-computer, wherein the portable device isconfigured for: receiving-from the on-board computer-preliminary squawkevents that occur while the aircraft is in flight; presenting thepreliminary squawk events; receiving approval inputs that indicateapproved squawk events of the preliminary squawk events; and generatinga squawk list that includes each of the approved squawk events to beinvestigated for corrective action after the flight.
 12. The system ofclaim 11, wherein the portable device is further configured forreceiving an edit input to change content of one of the preliminarysquawk events.
 13. The system of claim 11, wherein the portable deviceis further configured for receiving a removal input indicating a removedsquawk event of the preliminary squawk events that is not to be includedin the squawk list.
 14. The system of claim 11, wherein the portabledevice is further configured for presenting the preliminary squawkevents including presenting flight log data and information associatedwith each of the preliminary squawk events.
 15. The system of claim 11,wherein the portable device is further configured for, in response to arequest message communicated from the portable wireless communicationdevice, communicating the preliminary squawk events from the aircraft tothe portable device.
 16. The system of claim 11, wherein each of thepreliminary squawk events is either: a discrepancy that is observed by ahuman and manually entered by the human, wherein the discrepancy isflagged to be investigated for the corrective action after the flight;or added by an aircraft computer in response to a Crew Alerting System(CAS) message.
 17. The system of claim 11, wherein the portable deviceis further configured for: recording flight log data for the flight; andgenerating a final flight log based on the flight log data after theflight.
 18. The system of claim 17, wherein the portable device isfurther configured for: communicating the final flight log and thesquawk list from the portable device to a maintenance server by:communicating the final flight log and the squawk list from the portabledevice to the on-board computer; communicating the final flight log andthe squawk list from the on-board computer to a ground support networkfor the ground support network to communicate to the maintenance server,wherein the maintenance server automatically uploads and imports thefinal flight log and the squawk list into records associated with theaircraft.
 19. A portable device configured to communicate with acomputer of an aircraft, wherein the portable device is configured for:receiving preliminary squawk events-from the computer of theaircraft-that occur while the aircraft is in flight; presenting thepreliminary squawk events; receiving approval inputs that indicateapproved squawk events of the preliminary squawk events; and generatinga squawk list that includes each of the approved squawk events to beinvestigated for corrective action after the flight.